Relevant records

Relevant records describe the collection of rules that refine the behavior, presentation, and definition of a case or data type. They commonly designate records from an inherited class as important or reusable in a child class and to control the majority of the prompting and filtering in the Case Designer and Data Designer.

Relevant records for a case type can include references to properties, sections, flows, or flow actions that are explicitly important to your case. For example, properties marked as relevant define the data model of the case. Flows and flow actions marked as relevant appear in Case Designer prompts to encourage reuse. Sections marked as relevant appear as reusable views.

For a data type, relevant records designate the most important inherited fields for that data type. These records can include fields that are defined directly against the class of the data type and fields inherited from parent classes. View data types by their relevant records to see a complete and succinct data model for a data type.

You do not typically need to manually manage relevant records associated with a case or data type . Properties, sections, flows, and flow actions are automatically marked as relevant records when you create them within the Case Designer and Data Designer.

Relevant records control design-time prompting and filtering in several areas of the Data Designer and Case Designer.

Data Designer

• Designer Studio Data Designer provides the Show inherited and Show relevant records filter options.
• The Data Designer in express mode displays only relevant fields for the selected data type, with an option to display or hide relevant fields defined at inherited classes.

New fields you add to the data types in these areas are marked as relevant records.

Case Designer

• The Data model tab displays only relevant fields for the selected case type, with an option to display relevant properties defined at inherited classes.
• In Lifecycle, when you select an assignment and click Configure view, the Fields option sources properties from the relevant records on the current case type. Additional fields you add to a form are automatically marked as relevant for that case type.
• In Lifecycle > Add step, the Processes step palette sources flows from the relevant flows for the current case type; the User actions step palette sources flow actions from the relevant flow actions for the current case type. Additional steps (flow actions) you add to the case are automatically added to the relevant records for that case type.
• The Views tab displays the sections that are marked as relevant records for the current case type. Any additional views you create are automatically marked as relevant for the current case type.

Related information

Open topic with navigation